-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
32669 sumconnector config #33994
32669 sumconnector config #33994
Conversation
Regarding tests and the size of PRs: Is it cool to do tests in a separate PR from functionality? Edit to add: Is changelog required here if the component isn't live or wired in yet? |
This is fine for me since it's mostly test code. My preference is to keep functionality changes and the relevant tests in the same PR as much as possible. I'll review. As far as changelog, it's really just what's relevant to users. Announcing that a new component is being adding makes sense (the last PR), adding config validation not as much. I don't think a changelog is required here, but you're welcome to add one if you'd like. |
…me/opentelemetry-collector-contrib into 32669-sumconnector-config
From failing CI actions:
|
Test failures are frequencies of #33998, added reference there. |
Description: Fleshes out the config more fully and provides tests for the config and possible combinations of settings
Link to tracking Issue: #32669
Testing: Added test cases and testing for config
Documentation: No new documentation yet.